Associating a particular account configuration during the out of box experience for a mobile device

ABSTRACT

A method of providing particular account configurations to a user of a mobile device based on a predetermined account configuration offering between a mobile device manufacturer and a third-party service provider based on a code stored on the mobile device. During the out-of-box experience (OOBE) when the user is initially configuring the mobile device, the third-party provider receives user information, a code, and a mobile device identification number. The third-party service provider confirms that the mobile device is eligible for the particular account configuration by using the code and mobile device identification number. Once account configuration eligibility is confirmed, the third-party service provider associates the particular account configuration with either an existing user account or with a new user account established during the OOBE.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/923,181, filed Jun. 20, 2013, now U.S. Pat. No. 8,855,605, and claimsthe benefit of and priority to U.S. Provisional Patent Application No.61/705,458, filed Sep. 25, 2012, the contents of each of the abovepatent applications are hereby expressly incorporated by reference intheir entirety for all purposes herein.

BACKGROUND

Today's smart mobile devices can, and in some cases do, replace desktopand laptop computers. However, mobile devices have limited storage spacefor files, photos and videos. As a result, the mobile device hardwarelimits the user's ability to store files, photos, and videos on themobile device. In response to this need, some content managementservices now enable cloud-based cross-platform content synchronizationand sharing (e.g., Dropbox™), which enables users to convenientlyupload, store, and view files on any device associated with the account.

There are many competing cloud-based services and mobile users are freeto download any available third-party application and service. However,users must typically sift through hundreds of applications in anapplication store to find one that satisfies their needs. Moreover,application and service providers may struggle to differentiate in thishighly competitive market.

The present disclosure recognizes and addresses both the foregoing andother considerations of prior art system and methods in providing asolution to the limitations of the prior art.

SUMMARY

A computer-implemented method of associating a configuration with anaccount for a user by at least one processor, in various embodiments,may include receiving information from a mobile device. This informationmay include: (a) user information; (b) a mobile device identificationnumber; and (c) a code associated with an account configuration that ispreloaded in memory contained within the mobile device prior to the userreceiving the device. In response to receiving the information from themobile device, verifying, using the mobile device identification numberand the code, that the mobile device qualifies the user for a particularaccount configuration. Additionally, in response to verifying that themobile device qualifies the user for the account configuration,executing a step that is selected from a group consisting of: (a)associating the configuration with an existing user account based on theuser information, and (b) establishing a new account for a userassociated with the user information and associating the configurationwith the new account.

A mobile device, in various embodiments, may include: (1) at least oneprocessor; (2) memory operatively coupled to the at least one processor;and (3) a code stored in the memory. In some embodiments, at least oneprocessor may be configured to, upon initial activation setup of themobile device, receive information from a user and retrieve the codeassociated with an account configuration from the memory. Additionally,at least one processor may transmit the information, the code, and amobile device identification number to a third-party associated with thecode. The at least one processor may also receive deal information fromthe third-party confirming that the mobile device qualifies the user'saccount for the configuration. In response to receiving theconfiguration information from the third-party associated with the code,at least one processor may enable setup of a service associated with theaccount configuration on the mobile device.

BRIEF DESCRIPTION OF THE DRAWINGS

Various embodiments of a computer system for associating particularaccount configurations for a third-party service during an out of boxexperience for a mobile device are described below. In the course ofthis description, reference will be made to the accompanying drawings,which are not necessarily drawn to scale, and wherein:

FIG. 1 shows a block diagram of a content management system inaccordance with an embodiment of the present system;

FIG. 2 shows a block diagram of a computer that may be used, forexample, as a client or server computer within the context of thecontent management system of FIG. 1;

FIGS. 3-4 show flow diagrams that generally illustrate various stepsexecuted by a file sharing system in accordance with various embodimentsof the present system of FIG. 1; and

FIGS. 5-10 show screen shots from a mobile device that illustrate theuser experience associated with setting up a mobile device in accordancewith an embodiment of the present system and method.

DETAILED DESCRIPTION

Various embodiments will now be described. It should be understood thatthe present disclosure may be embodied in many different forms andshould not be construed as limited to the embodiments set forth herein.Like numbers refer to like elements throughout.

System Overview

The present disclosure, in accordance with various embodiments, providesa content management server that may receive information from a mobiledevice during the device's initial activation and setup. In severalembodiments, during the device initial setup, the content managementserver verifies that the user and device qualify for a predeterminedaccount configuration for a third-party service. For example, thecontent management server may verify that the user and device qualifyfor an account configuration by: (1) receiving a code and otherinformation and recording it in a log; and (2) processing the log toaward the account configuration by verifying other information provided.In various embodiments, the information received by the contentmanagement server may include user information, a code preloaded on themobile device, and a unique mobile device identification number. Thecontent management server may associate the account configuration withan existing user account for the service or with a new user account forthe service that is established during setup of the mobile device. Itshould be understood that a code can take any appropriate form. Invarious embodiments, the code may be represented by a unique series ofnumbers and letters, a special type of file (e.g., a Java Archive file),or a calculated hash value based on various collected user data.Additionally, the code may be unique to a specific device or the samefor each device manufactured by a particular company. The contentmanagement server may determine whether the code is valid for theidentified mobile device and user and grant a particular accountconfiguration for the service to the user.

In various embodiments, the account configuration may include grantingthe user of the mobile device free cloud-based storage space on thecontent management system. Cloud-based storage space is advantageousbecause storage space on mobile devices may be limited. Thus, in someembodiments, from a high level, if the content management serververifies that the device and the user qualify for the free cloud-basedstorage space, the content management server grants the storage space tothe user. More specifically, in various embodiments, an applicationassociated with the content management server is pre-loaded on a mobiledevice. In several embodiments, when a user is setting up the mobiledevice, the application “fetches” or accesses a file on the device. Theapplication may then send user information, device information, and anassociated code to the content management server. Then, the contentmanagement server either associates the granted cloud-based storagespace with an existing user account of the user or with a new useraccount that is created during the setup of the mobile device.

In other embodiments, the content management server may grant aparticular account configuration after the user satisfies apredetermined criterion. For example, if the user and the device qualifyfor the account configuration, then the account configuration isassociated with the user account after the user completes a “gettingstarted” tutorial for the content management system. Once the contentmanagement server verifies the device and the user information, thecontent management server sends a notification back to the mobile deviceto notify the user that they qualify for the particular accountconfiguration.

The present invention is advantageous because the third-party service isintegrated into the out-of-box experience for the mobile device. Forpurposes of this disclosure, the term out-of-box experience (OOBE) is aterm that describes the experience that a consumer (or user) has whenfirst performing the initial setup and configuration of a mobile device.Because the third-party service is integrated into the OOBE, thethird-party gains an advantage over other application and serviceproviders by getting the user to sign up for, and use, the third-partyapplication and related service.

Exemplary Technical Platforms

The present invention may be, for example, embodied as a computersystem, a method, or a computer program product. Accordingly, variousembodiments may be entirely hardware, entirely software, or acombination of hardware and software. Furthermore, particularembodiments may take the form of a computer program product stored on acomputer-readable storage medium having computer-readable instructions(e.g., software) embodied in the storage medium. Various embodiments mayalso take the form of web-implemented computer software. Any suitablecomputer-readable storage medium may be utilized including, for example,hard disks, compact disks, DVDs, optical storage devices, and/ormagnetic storage devices.

Various embodiments are described below with reference to block diagramsand flowchart illustrations of methods, apparatus (e.g., systems), andcomputer program products. It should be understood that each element ofthe block diagrams and flowchart illustrations, and combinations ofelements in the block diagrams and flowchart illustrations,respectively, can be implemented by a computer executing computerprogram instructions. These computer program instructions may be loadedonto a general purpose computer, a special purpose computer, smartmobile device, or other programmable data processing apparatus toproduce a machine. As such, the instructions which execute on thegeneral purpose computer, special purpose computer, smart mobile device,or other programmable data processing apparatus create means forimplementing the functions specified in the flowchart block or blocks.The program code may execute entirely on the user's computer, partly onthe user's computer, as a stand-alone software package, partly on theuser's computer and partly on a remote computer, or entirely on theremote computer or server. In the latter scenario, the remote computermay be connected to the user's computer through any type of network,including a local area network (LAN) or a wide area network (WAN), orthe connection may be made to an external computer (for example, throughthe Internet using an Internet Service Provider).

These computer program instructions may also be stored in acomputer-readable memory that can direct a computer or otherprogrammable data processing apparatus to function in a particularmanner such that the instructions stored in the computer-readable memoryproduce an article of manufacture that is configured for implementingthe function specified in the flowchart block or blocks. The computerprogram instructions may also be loaded onto a computer or otherprogrammable data processing apparatus to cause a series of operationalsteps to be performed on the computer or other programmable apparatus toproduce a computer implemented process such that the instructions thatexecute on the computer or other programmable apparatus provide stepsfor implementing the functions specified in the flowchart block orblocks.

Accordingly, block diagram elements and flowchart illustrations supportcombinations of mechanisms for performing the specified functions,combinations of steps for performing the specified functions, andprogram instructions for performing the specified functions. It shouldalso be understood that each block diagram element and flowchartillustration, and combinations of block diagram elements and flowchartillustrations, can be implemented by special purpose hardware-basedcomputer systems that perform the specified functions or steps, orcombinations of special purpose hardware and other hardware executingappropriate computer instructions.

Exemplary System Architecture

FIG. 1 is a block diagram of content management system 100 according toa particular embodiment. As may be understood from this figure, contentmanagement system 100 includes remote computing devices such as tabletcomputer 102, desktop or laptop computer 104, or mobile computing device106 (e.g., a handheld device, a laptop, a tablet computer, a cellularphone, a smart phone, or any other device capable of transferring filesover network 110) that are in communication with content managementserver 112 (which, for example, may be used to execute one or moremodules as described below) and content management database 114 (which,for example, may be used to store the files on the content managementsystem) via one or more networks 110. Networks 110, between contentmanagement server 112 and client devices 102, 104, and 106, may be, forexample, implemented via one or more wired or wireless networks such asLANs, WANs, a cellular network, a Wi-Fi network, or via the Internet.For purposes of ease of explanation and clarity, no specific cellularnetwork is shown in FIG. 1 as a network for a mobile device. However, acellular tower may be coupled to a cellular network provider, which maybe operatively coupled to network 110. The users of each of tabletcomputer 102, desktop computer 104, and mobile device 106 may have filestorage accounts on content management server 112.

Network 110 may include any of a variety of types of wired or wirelesscommunication networks, such as the Internet. The communication linkbetween content management server 112 and content management database114 may be, for example, implemented via a LAN, WAN, or via theInternet. Mobile device 106 may transmit data wirelessly over cellularnetwork by communicating with a cellular tower 108. For purposes of easeof explanation and clarity, cellular tower 108 is shown coupled tonetworks 110. However, the cellular tower may be coupled to a cellularnetwork provider, which is operatively coupled to network 110.

In various embodiments, content management server 112 may include one ormore servers that are located in close physical proximity, or someservers may be locally together and others remote. In either case, alldevices, wherever located, function as a system.

Content management server 112 enables file access and file storagebetween content management server 112 and client devices remotecomputing devices 102, 104, and 106. Content management server 112receives files from and sends files to remote computing devices 102,104, 106 consistent with the user's preferences for sharing files.Content management server 112 may act as the counterpart to aclient-side file storage service client application user interface thatallows a user to manipulate files directly stored on content managementserver 112. In some embodiments, software operating on remote computingdevices 102, 204, 106 integrates network-stored files with the client'slocal file system to enable a user to manipulate network-stored filesthrough the same user interface (UI) used to manipulate files on thelocal file system, e.g., via a file explorer, file finder or browserapplication. As an alternative or supplement to the client-side fileexplorer interface, content management server 112 may provide a webinterface for remote computing devices 102, 104 106 to access (e.g. viaa web browser) and allow a user to manipulate files stored on contentmanagement server 112. In this way, the user can directly manipulatefiles stored on content management server 112.

In various embodiments, content management database 114 stores filessuch as those uploaded using remote computing devices 102, 104, 106. Itshould be understood that, in various embodiments, content managementdatabase 114 may include of multiple data stores—some local to, and someremote from, content management server 112.

Content management database 114 maintains, for each user in a filejournal, information identifying the user, information describing theuser's file directory, etc. In some embodiments, the file journal ismaintained on content management server 112. This file journal may beupdated periodically using information obtained directly from contentmanagement server 112 and/or from information obtained from one or moreclient devices 102, 104, and 106 linked to the user's account. In thisway, the server-stored file journal (hereinafter the “server-side filejournal”) is updated when a file is changed either on the server or onone of the client devices associated with the user's account. When afile is changed, content management server 112 propagates the change toeach client device associated with the user's account. For example, if auser makes a change to a particular file on a first client device, thechange may be reflected in the server-side file journal. The system thenuses the server-side file journal to propagate the change to all clientdevices associated with the user's account. Such techniques may beimplemented, for example, within the context of a synchronized filesystem such as the Dropbox™ Service of Dropbox, Inc. of San Francisco,Calif.

FIG. 2 illustrates a diagrammatic representation of computer 200 thatcan be used within content management system 100, for example, as clientcomputer 102, 104, or 106 (FIG. 1), or as content management server 112(FIG. 1). For purposes of this disclosure, reference to a server orprocessor, shall be interpreted to include either a single server, asingle processor, or multiple servers, or multiple processors.

In particular embodiments, computer 200 may be connected (e.g.,networked) to other computers by a LAN, WAN, an intranet, an extranet,and/or the Internet. Computer 200 may operate in the capacity of aserver or a client computer in a client-server network environment, oras a peer computer in a peer-to-peer (or distributed) networkenvironment. Computer 200 may be a personal computer (PC), a tablet PC,a mobile device, a web appliance, a server, a network router, a switchor bridge, or any computer capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatcomputer. Further, while only a single computer is illustrated, the term“computer” may also include any collection of computers thatindividually or jointly execute a set (or multiple sets) of instructionsto perform any one or more of the methodologies discussed herein.

Exemplary computer 200 may include processor 202, main memory 204 (e.g.,read-only memory (ROM), flash memory, dynamic random access memory(DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.),static memory 206 (e.g., flash memory, static random access memory(SRAM), etc.), and data storage device 218, which communicate with eachother via bus 232.

Processor 202 may represent one or more general-purpose processingdevices such as a microprocessor, a central processing unit, or thelike. More particularly, the processing device may be a complexinstruction set computing (CISC) microprocessor, reduced instruction setcomputing (RISC) microprocessor, very long instruction word (VLIW)microprocessor, or processor implementing other instruction sets, orprocessors implementing a combination of instruction sets. Processor 202may also be one or more special-purpose processing devices such as anapplication specific integrated circuit (ASIC), a field programmablegate array (FPGA), a digital signal processor (DSP), a networkprocessor, or the like. Processor 202 may be configured to executeprocessing logic 226 for performing various operations and stepsdiscussed herein.

Computer 200 may further include a network interface device 208.Computer 200 also may include video display 210 (e.g., a liquid crystaldisplay (LCD) or a cathode ray tube (CRT)), alphanumeric input device212 (e.g., a keyboard), cursor control device 214 (e.g., a mouse), andsignal generation device 216 (e.g., a speaker).

Data storage device 218 may include machine accessible storage medium230 (also known as a non-transitory computer-accessible storage medium,a non-transitory computer-readable storage medium, or a non-transitorycomputer-readable medium) on which is stored one or more sets ofinstructions (e.g., a deal verification module, which is configured tocarry out the steps illustrated in FIG. 3 or a software initiationmodule, which is configured to carry out the steps illustrated in FIG.4) embodying any one or more of the methodologies or functions describedherein. The deal verification module may also reside, completely or atleast partially, within main memory 204 and/or within processing device202 during execution thereof by computer 200, main memory 204, andprocessing device 202 also constituting computer-accessible storagemedia. Instructions 222 (e.g., file organizing module 29) may further betransmitted or received over network 220 via network interface device208.

While machine-accessible storage medium 230 is shown in an exemplaryembodiment to be a single medium, the term “machine-accessible storagemedium” should be understood to include a single medium or multiplemedia (e.g., a centralized or distributed database, and/or associatedcaches and servers) that store the one or more sets of instructions. Theterm “machine-accessible storage medium” shall also be understood toinclude any medium that is capable of storing, encoding, or carrying aset of instructions for execution by the computer and that cause thecomputer to perform any one or more of the methodologies of the presentinvention. The term “computer-accessible storage medium” shallaccordingly be understood to include, but not be limited to, solid-statememories, optical, and magnetic media.

Exemplary System Operation

Devices 102, 104, 106 and content management server 112 may alone, or incombination, perform the method steps of FIGS. 3 and 4. It should beunderstood by reference to this disclosure that these methods describeexemplary embodiments of the method steps carried out by the presentsystem, and that other exemplary embodiments may be created by addingother steps or by removing one or more of the method steps described inFIGS. 3-4.

FIG. 3 shows the steps provided by exemplary verification module 300 fordetermining whether a new or inactivated mobile device and user of suchdevice are eligible for a particular account configuration with athird-party service provider. Beginning at step 302, the contentmanagement server may receive information from a mobile device, whichmay be transmitted over a cellular connection or over a Wi-Fi connectionthat may be established during the setup of the mobile device. Theinformation sent to the content management server may be sent inresponse to the user entering the information during the setup of themobile device. In various embodiments, the information may contain: (1)user information; (2) a code that is preloaded on the mobile device bythe manufacturer of the mobile device or by a wireless carrierassociated with the mobile device; and (3) a unique mobile deviceidentification number.

In some embodiments, the user information may include a username andpassword. The username may be, for example, an e-mail address or anysuitable username accepted by the third-party service provider (e.g.,the content management server of a content management system). Invarious embodiments, the unique mobile device identification number maybe the electronic serial number for the mobile device. In otherembodiments, the mobile identification number may be any other suitableidentifier that allows the content management system to track anindividual mobile device.

In various embodiments, the code may be a unique code associated withthe manufacturer and model of the mobile device. That is, the same codemay be used on all like models of the mobile device. In otherembodiments, the code may be associated with the wireless carrier thatprovides cellular service to the mobile device. As discussed above thecode may be preloaded onto the mobile device prior to the mobile devicebeing shipped to the retail seller (e.g., by the manufacturer or otherintermediary). The code may be stored in the mobile device memory in afile such as a Java Archive file. In various embodiments, the code maybe encrypted to help prevent unauthorized use of the code.

Once the content management server 112 receives the information from themobile device, in response to receiving the information, at step 304,the content management server may verify that the mobile devicequalifies the user for the account configuration. In variousembodiments, the account configuration may relate to a third-partyservice that is provided to the user of the mobile device. Thus, basedon the information received from the mobile device, the contentmanagement server, in various embodiments, may confirm that: (1) thecode on the mobile device qualifies the user for a particular accountconfiguration; (2) that the particular account configuration was notalready granted to another user of the mobile device; (3) and in someembodiments, that the user has satisfied at least one criterion. Thecriterion may be, for example, the completion of a tutorial on thethird-party service.

At step 304, content management server 112 may determine whether themobile device qualifies for the account configuration based on the code(e.g., is the code being used on a qualified mobile device) and themobile device identification. If the mobile device qualifies for theaccount configuration, then at step 306, the content management servermay determine whether the user associated with the mobile devicequalifies for the account configuration. In various embodiments, adevice may qualify for the account configuration if the devicemanufacturer predetermines an account configuration with the third-partyvendor providing the content management system services. If, on theother hand, the mobile device does not qualify for the accountconfiguration (e.g., the code is not being used on a qualified mobiledevice), at step 310, the content management server may notify the userthat they do not qualify for the particular account configuration.

At step 306, content management server 112 also may determine if theuser qualifies for the account configuration. If the user does notqualify for the account configuration, the content management servermoves to step 310 and notifies the user that they do not qualify for theaccount configuration. In various embodiments, a user may not qualifyfor a particular account configuration, even though the mobile devicedoes qualify for the particular account configuration. This may happen,for example, if the user previously was granted the particular accountconfiguration on another qualifying mobile device.

If, on the other hand, the user qualifies for the account configuration,then at step 308, the content management server may determine if theuser is new to the content management system or has an existing accounton the content management system. In various embodiments, the user canindicate if they are an existing or new user when setting up the mobiledevice. For example, the third-party service screen in the OOBE mayallow the user to select “I already have an account” menu item 904 (FIG.9) or “Create a new content management service account” menu item 902(FIG. 9). As such, in various embodiments, the user information receivedby the content management server may contain an indication whether theuser is a new or an existing user to the content management system. Ifthe user is setting up a new account, the content management server, atstep 314, may create the new account and associates the particularaccount configuration with the new user account. Otherwise, at step 312,the content management server may log the user into their existingaccount and associates the particular account configuration with theuser's existing account.

In various embodiments wherein the particular account configuration isnot associated with the user's account, the content management servermay associate the device with either a new or existing account for theuser even though the user does not qualify for the deal. In this way,the user may receive the standard account configuration, but gain thebenefit of using the content management services with the mobile device.

In various embodiments, the user information, code, and mobile deviceidentification number may be stored in content management database 114.Alternatively, the particular account configuration associated with theuser's account can also be stored in content management database 114.This way, content management server 112 can manage the user's accountwith respect to the particular account configuration granted to theuser. For example, in some embodiments, the particular accountconfiguration may grant the user a predetermined amount of free storagespace on a synched content management system for a fixed length ofservice. Content management server 112 may use the stored information tomanage the user's account and provide renewal notice when the fixedlength of service expires. The user and device information stored incontent management database 114 may allow content management server 112to sync file data among different client devices associated with theuser's account.

FIG. 4 shows a method, in accordance with various embodiments of amobile device, of associating an account configuration with the accountof a user of the mobile device. Beginning at step 400, mobile device 106(FIG. 1) may receive information from user 402. The information may bereceived during the initial setup of the mobile device. In particular,one or more screens in the mobile device OOBE may present the user ofthe mobile device with the opportunity to initiate a third-party serviceon the mobile device. For example, in one embodiment, the third-partyservice may be a cloud-based content management service where photos,files, and videos are stored by the third-party content managementserver and are made available to the user of the mobile device. Thisway, the files, photos, and videos may not deplete the memory on themobile device and may be downloaded in real time when the user wants toview or edit a file.

At step 404, in response to receiving the information from the user, themobile device may retrieve a code from memory in the mobile device. Thecode may be included in a file stored on the mobile device. For example,in various embodiments, the code may be stored within a Java Archivefile. The code may be a unique code that associates particular accountconfigurations with a particular mobile device model or wirelesscarrier. As such, in various embodiments, the third-party serviceprovider may predetermine certain account configurations with a mobiledevice manufacturer and/or wireless carrier. In exchange for providingadvantageous account configurations to the mobile device user, invarious embodiments, the manufacturer may integrate the third-partyservice provider application and service setup screens into the mobiledevice OOBE.

At step 406, the mobile device may transmit the user information, thecode and a mobile device identification number to a third-party serviceprovider associated with the code. At step 408, the mobile device mayreceive information from the third-party confirming that the mobiledevice qualifies for the account configuration. At step 410, in responseto receiving information from the third-party associated with the code,the mobile device may enable the setup of the service (for example,synching data on a content management system or auto-populating photogallery views on the mobile device) on the mobile device.

In various embodiments, the code may be associated with the provision offree cloud-based storage space on a content management system. In someembodiments, the content management system may be a synched contentmanagement system. In still other embodiments, the service on the mobiledevice may automatically populate a photo gallery view on the mobiledevice or automatically uploads files from the mobile device to thecontent management system once the service is setup on the mobiledevice.

Example User Experience

When a user purchases a mobile device, in most cases, the user mustsetup the mobile device prior to using the device, which is performed bythe user through the mobile device's OOBE. Setup is performed bynavigating through one or more setup screens that allows a user toselect options to customize the mobile device to their liking. Thefollowing discussion is directed to various embodiments of an OOBE thatthe user may experience when setting up their mobile device.

Referring to FIG. 5, when the user powers on the mobile device for thefirst time, the mobile device may present the user with welcome screen500. The user may select their local language and select “start” menuitem 502 to advance to the next screen. Referring to FIG. 6, in someembodiments, the user may also select the mobile network on “Simservice” screen 600. Once the user selects the mobile network provider,they may select “start” menu item 602 to continue the setup process.

Referring to FIG. 7, the mobile device presents the user with devicemanufacturer account screen 700 that may allow the user to associate themobile device with an account hosted by the mobile device manufacturer.In the example shown, the user may either set up an account with amobile device manufacturer by clicking “create account” menu item 702,or log into an existing mobile device manufacturer account by selecting“sign in” menu item 704. The user may already have a mobile devicemanufacturer account if they have previously owned a mobile devicemanufactured by the same company. Referring to FIG. 8, once the userlogs into an existing account or creates a new account, backup screen800 may be displayed that allows the user to backup and restore SMSmessages, call logs, and certain settings by selecting items on “backup”screen 802. Thus, if the user has to reset the mobile device for anyreason, or if the user buys a new mobile device, the user can restoresaved information to the new device, or the reset old device. Once theuser selects their backup settings, the user may hit “ok” menu item 804to advance to the next screen.

In various embodiments, the OOBE may be configured to present the userwith the ability to associate the mobile device with a third-partyservice provider. In particular, and referring to FIG. 9, contentmanagement service screen 900 presents the user with an accountconfiguration that relates to the provision of a predeterminedconfiguration package, such as free cloud-based storage space with anaccount on a synched content management system (e.g., Dropbox, Inc.). Inthe current example, the manufacturer of the mobile device negotiated anaccount configuration with content management service to provide theuser with 50 free GB of cloud storage on the content management servicesynched content management system. To take advantage of thisconfiguration, screen 900 provides the user with an option to create anew account by selecting “Create a new content management serviceaccount” menu item 902 or to log into an existing content managementservice account by selecting “I already have an account” menu item 904.The user may also select “No thanks” menu item 906, which allows theuser to skip over the account configuration offering. However, if theuser selects “No thanks” menu item 906, they can later return to thismenu option to take advantage of the account configuration offering. Ifthe user already has a content management service account, the contentmanagement service system will associate the account configuration withthe user's existing account. Associating the mobile device with acontent management service account allows the user to store data files,including photos and video in their cloud-based storage account. In thisway, the user can maximize the amount of local memory that is availableto the user while maintaining the ability to view and download contentas needed.

Once the user is finished creating a new content management serviceaccount or logging in to their existing account, referring to FIG. 10,the OOBE presents the user with camera upload screen 1000 that allowsuser enable an automatic photo upload feature by selecting “Turn on”menu item 1002. If the user does not wish to enable the photo uploadfeature, they can select “Skip” menu item 1004 to advance to the nextscreen. The camera upload feature allows the mobile device toautomatically send photos, videos, and screenshots taken on the mobiledevice to a private folder in the user's content management serviceaccount.

One of skill in the art, with reference to this disclosure, shouldunderstand that various other OOBE screens may be included in the setupand initialization of the mobile device.

CONCLUSION

Having the benefit of the teachings presented in the foregoingdescriptions and associated drawings, one of skill in the art willrecognize many modifications and other embodiments of the invention.

In light of the above, it is to be understood that the invention is notto be limited to the specific embodiments disclosed and thatmodifications and other embodiments are intended to be included withinthe scope of the appended claims. Although specific terms are employedherein, they are used in a generic and descriptive sense only and notfor the purposes of limitation.

What is claimed:
 1. A computer-implemented method of associating anaccount configuration with an account for a user by at least oneprocessor, comprising the steps of: receiving information from a mobiledevice, wherein the information comprises: user information; a mobiledevice identification number; and a code that is preloaded in memorycontained within the mobile device prior to the user receiving thedevice; wherein the code is associated with the account configurationand the account information is associated with a free cloud-base storagespace provided to the user for a fixed period of time and a renewalnotice is provided when the fixed period of time expired; in response toreceiving the information from the mobile device, verifying, using themobile device identification number and the code, that the mobile devicequalifies the user for the account configuration; and in response toverifying that the mobile device qualifies the user for the accountconfiguration, prompting the user to select: associating the accountconfiguration with an existing user account based on the userinformation, and establishing a new account for the user associated withthe user information and associating the account configuration with thenew account.
 2. The computer-implemented method of claim 1, wherein theuser information further comprises a username and a password.
 3. Thecomputer-implemented method of claim 1, wherein the mobile deviceidentification number is unique to the mobile device.
 4. Thecomputer-implemented method of claim 1, further comprising the step ofsending a notification to the user of the mobile device that at leastone criterion must be satisfied prior to receiving the accountconfiguration.
 5. The computer-implemented method of claim 1, whereinthe account is an account on a synched content management system.
 6. Thecomputer-implemented method of claim 1, wherein the code is included ina file that is preloaded on the mobile device before the mobile deviceis shipped to the user.
 7. The computer-implemented method of claim 6,wherein the file is a Java Archive file.
 8. The computer-implementedmethod of claim 1, further comprising: confirming if the user hassatisfied at least one criterion; and a step selected from the groupconsisting of: providing the account configuration to the user if the atleast one criterion has been satisfied, and sending notification to theuser that the at least one criterion must be satisfied prior toproviding the account configuration to the user.
 9. A mobile devicecomprising: at least one processor; memory operatively coupled to the atleast one processor; a code stored in the memory, wherein the code isassociated with a particular account configuration and the particularaccount information is associated with a free cloud-base storage spaceprovided to a user for a fixed period of time and a renewal notice isprovided when the fixed period of time expired; wherein the at least oneprocessor is configured to, upon initial activation setup of the mobiledevice: receive information from the user; retrieve the code associatedwith a service from the memory; transmit the information, the code and amobile device identification number to a third-party associated with thecode; receive account configuration information from the third-partyconfirming that the mobile device qualifies the user for the particularaccount configuration; and in response to receiving the accountconfiguration information from the third-party associated with the code,prompting the user to select: associating the account configuration withan existing user account based on the user information, and establishinga new account for the user associated with the user information andassociating the account configuration with the new account.
 10. Themobile device of claim 9, wherein the code is contained in a JavaArchive file.
 11. The mobile device of claim 9, wherein the informationcomprises a username and a password.
 12. The mobile device of claim 9,wherein the at least one processor is further configured toautomatically populate information on the mobile device once the serviceis set-up.
 13. The mobile device of claim 9, wherein the code isretrieved in response to receiving the information from the user. 14.The mobile device of claim 9, wherein the mobile device is a handhelddevice.
 15. A system, comprising at least one processor configured toprovide a user of a mobile device a particular account configuration fora service based on a code stored on the mobile device and in context ofthe user initially setting up the mobile device, comprising: receivinginformation from the mobile device when the user is initially setting upthe mobile device, wherein the information comprises: a mobile deviceidentification number; user information; and the code, wherein the codeis associated with the account configuration and the account informationis associated with a free cloud-base storage space provided to the userfor a fixed period of time and a renewal notice is provided when thefixed period of time expired; in response to receiving the informationfrom the mobile device, confirming, using the information, that the userof the mobile device is eligible for the particular accountconfiguration for the service; in response to confirming that the useris eligible for the particular account configuration, granting theparticular account configuration to the user; and prompting the user toselect: associating the account configuration with an existing useraccount based on the user information, and establishing a new accountfor the user associated with the user information and associating theaccount configuration with the new account.
 16. The system of claim 15,wherein the account is an account on a synched content managementsystem.
 17. The system of claim 15, wherein the code is included in afile that is preloaded on the mobile device prior to the mobile devicebeing provided to the user.